fix(ux): use %w for proper error chain wrapping#134
Conversation
Replace %v with %w in fmt.Errorf calls so callers can use errors.Is/As
to inspect underlying errors. Simplify redundant fmt.Errorf("%v", err)
to return err directly.
✅ Deploy Preview for devsydev canceled.
|
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 31 minutes and 23 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
1 participant
Summary
%vwith%winfmt.Errorfcalls acrosspkg/util/hash/hash.goandpkg/command/credential_supported.goso callers can useerrors.Is/errors.Asto inspect underlying errorsfmt.Errorf("%v", err)inpkg/survey/survey.gotoreturn errdirectly, preserving the error chain without a redundant wrapper